Almathera Ten Pack 3: CDPD 3

home *** CD-ROM | disk | FTP | other *** search

/ Almathera Ten Pack 3: CDPD 3 / Almathera Ten on Ten - Disc 3: CDPD3.iso / scope / 051-075 / scopedisk72 / tag-25 / tag-upgrade.doc < prev next >

Wrap

Text File | 1995-03-19 | 33KB | 606 lines

This file is the TALE-of-the-UPGRADE-Path . It is the cronology of just exactly is different from rev to rev... in case you have a back dated revision. Much work has gone into NOT invalidating your board's database while consistatantly allowing you access to the latest I can pack into the TAG system!! +---------------------------------------+ | The information is provided in the | | REVERSE order.. newest FIRST!! | +---------------------------------------+ REV 2.50a/b 3/5/89 c=3/6/89 d=3/7/89 e=3/8/89 f=3/9/89 A new parameter must be placed in the TAG_LIBRARIES file. It is MAX_DL_PER_DAY: and should be followed by a number. This is the maximum number of files any user can download from your board in any 12 hour period. If you want to disable this feature.. put a BIG number in here!! A feature is added to allow a user to reply directly to the user that uploaded a file. This will be ESPECIALLY appreciated by you sysops. It will allow you direct communication if the file turns out to be a bad archive. This will be found at the <L>ist prompt. Along with this.. the reply SUBJECT: is automatically filled in with the filename.. and the reply for a new user to the sysop is ALSO filled in. This should help you identify when you have a new user to validate. A minor adjustment of the 'Press RETURN' at logon should furthur insure the user is stabilized on the line. A change has been implimented to place the LIBRARY's name in the TAG_UPLOAD_LOG to facillitate location of the latest uploads. This will not affect anything.. except the library's name will appear on the same line in the log as the filename. Should be self explainatory. Also, if a 'duplicate filename' is found.. the duplicate file and its description is displayed!! Just in case your user has just picked a bad name for a file that he has as something else. REV 2.50/2.49/b/c/d/e (sorry.. all in 3 days!!!) 3/1/89 The AUTO edit has been improved.. it doesn't take all the time it used to.. it is abortable... and it has a few more options!! The <N>ew prompt at the libraries does not call to the routine to allow you to SET your NEW POINT.. so now you have to do any setting through the GLOBAL new on the main menu. The stats package does not printout all the names and stats during the read of your user database.. which may make it much more friendly for a large database for a remote sysop. f= The 'press return' prompt finally does something!! It will allow 3 tries and will ACTUALLY hangup if it is not satisfied. Also.. if your caller slips into a data-streaming mode in his callin... the bbs will abort him at the logon prompt. e= You must put another parameter in the TAG_SYSTEM file. It is "CHATLEVEL:" and the number you put AFTER it will determine what minimum security level users can use the CHAT request. A -1 will allow all!! A 2 will only allow VALIDATED users the CHAT requestor!! d= The history stats (both on the idle screen and the tag_use_log) has been adjusted to report ONLY the activity that took place on THAT particular visit. It is felt this data is of much more use to the sysop. If you need the TOTAL number of uploads/downloads/mail etc.. check your user's stats. Also... a minor omission was fixed.. FEEDBACK to sysop was not being reported as mail sent in his user statistics. c= True to my promise of support with a smile... The feature has been added for a user to change his info.. Name, Password..etc.. with the stipulation that he IMMEDIATELY reverts to NEW and will have to be validated once again. The only thing he CAN change without reverting.. is his password.. but if he even OFFERS to change anything else.. his account will revert!! A minor bug was reported and fixed. The file modes on the mail <E>xtract function were not correct. If you saved a piece of mail to an existing file it would hang... now it will simply append to it. REV 2.48 3/89 The WORKPATH: parameter's influence has been extended to the <S>tatistics off the Main menu. This is provided as another help to our 512K users. All the magic done by the stats package will now be done on the WORKPATH: directory.. not (as defaulted to earlier) on the RAM disk! Some verbage inconsistancies have been cleaned up. The NOTE message when you <E>vissorate a file to the end that "its still there" seemed to 'confuse' some sysops.. its wording is changed!! The System-Fallow seemed to be getting a little out of line.. making some VERY large numbers appear. I may have uncovered the problem.. but time (lil' joke..) will tell!! The 'JOIN' proceedure has, once again, been tweeked!! There is a NEW parameter in the TAG_SYSTEM file "BNAMEPROMPT:"!! After this.. you may place any phrase (up to 60 characters) that you feel is appropriate for your users.. such as..... Enter your BOARD name (ALIAS) MAX 14 Characters or Enter your First Initial and LAST name(max 14 chars) The actual data entry is made MORE foolproof!! They are given a template to type into.. and more exact prompts!! REV 2.47 2/89 Apparently there some real jerks out here. A sysop has pointed out some ways to 'crash' TAG.. These are addressed here.. and fixed!! Also.. the <A>uto upload for sysops now includes a prompt to input the ACCESS code you want to have assigned this file. If you want this file to be completely under the special '3' access umbrella.. you must also give the file an access code of '3'!! REV 2.46 2/89 Finally, a way to save your Library structure and restore it. The most important use will be allow you to... 1. save off the structure. 2.erase the library.keys (where the structure is kept) 3.Change the SIZE/Location of your library (perhaps you get another disk drive) 4.Regenerate 5. Re-import the old data into the newly created library structure. (note.. you can also merge structures as easily). It also allows a simple method of "saving" your library structure. These are found in the Library Maintain menu. REV 2.45 2/89 A number of people are having problems with the <V>iew option on the libraries. This is FIXED!!! In the TAG_LIBRARIES file there is a new parameter called 'WORKPATH:'. If you needy for space in ram: (as it was defaulted to there... ) you can create a directory on PHYSICAL DISK for the ARC AND ZOO to do its magic. It should be an EMPTY directory.. include the FULL path to it (including an ending ':' or '/'!!). Keep in mind that this may slow up the process if it on floppy.. but then floppies should not have files on them anyhow... right?? REV 2.44 2/89 A minor bug is fixed. When you did the USER stats.. the last user never was included. This is now fixed. Another minor bug fixed. The <A>ccount stats would report wrong figures in certain situations.. mostly REPETITIVE figures.. "111" or "2222" etc. This is now fixed. This bug is a Lattice bug and has been there since 2.xx of the Lattice compiler. REV 2.43 1/89 An obvious QUIT was added to the TRIVIA main menu/prompt. Due to increased preasure.. the present x-modem is under scrutiny. I beleive I have found a bug in the 'timeout' of downloads from tag. It should now abort MUCH sooner!! Also the requirement that a downloader enter 4-5 CONSECUTIVE control-X's to abort has been added to keep potential line noise from inadvertinately aborting the download!! Express mail has been modified. If you put a '2' in the Express parameter in the tag_system file... Express mail will be placed on ALL mail correspondence. It is felt that this, if allowed, will improve chances of getting mail read and deleted. A really nice little piece of code has been added to make a File-list exactly like you see when you do a <C>atalog. It is located in the <M>aintain menu.. and it will create a file on that library's directory called FILE-LIST. This file will not be ARC'd or ZOO'd but if it appears in that directory when you enter the Library as a user.. you will have an extra prompt '<R>eceive filelist via xfer protocol'. It is suggested that you do an ARC or ZOO on this file and then DELETE it.. and the prompt will go away. If you leave it.. ANYONE who sees it will be permitted to download it.. regardless of time left or security. This list does NOT include the files in the '3' special security sub-lib!! ======== END OF 2.43 ========= REV 2.42 Account data standardization is implimented.The boardname (alias) is ALWAYS in UPPERCASE.. the fullname,address,citystate are always set as they should be.. 1st letter caps.. the rest as lower!! The only abnormality is the 2 letter state is 1-upper,1-lower.. but they are, at least, standardized!! You do not have to go back and edit your present users.. they are re-filtered every time they are accessed!! REV 2.41 Support for blocks free in the Libraries. Your users will always know if there is room for an upload. Rev 2.41b.. This is for testing purposes for those with the modem.. hangup problem. What is added are 2 more commands in the Await Logon mode. You can see them by typing '?<return>'. What these are.. are D and E. "D" will attempt to read out all of you modem's S registers.. and display them all at once in the window. After several attempts at delays and multiple this and thats... I came to the conclusion that we are saddled with the most unreliable communication devices that could be made. So.. to counter this... I include "E".. which is an Examine of a single (prompted for) S register.. and display its contents in decimal and Hex!! When your modem is not listening to you or the phone... examine a few key registers to find out what is making this happen... and report your findings via CAB BBS!! When you do report.. please send the EXACT model of your modem, The exact SETUP string you azre using.. and a PRECISE description of the problem.. and whatever dump (examine) data you got!! I must solve this before I can release the y/z modem... or we are in for an impossible seige!! I do not have access to modems as diverse as my users.. but I care.. and with some truly ACCURATE reporting... we will solve this!! REV 2.40 More bugs!! A small bug surfaced when I installed the questions in the trivia database since a question can have 80 characters.. and answers are limited to 40 characters. Apparently my docs to people wjho have submitted files of questions may hav missed this. Anyway.. now it is protected!! You should delete your Trivia.data file and re-run Generate!! Don't worry.. you won't hurt anything.. only the trivia database will be cleared!! Then re-import the trivia-in file (from the S: directory)! REV 2.39 WOW.. finally something new... I have been getting upset when someone uploads a file my bbs already has. Either the user renames the file or sends the ZOO'd version while I have the ARC'c version.. Well.. no more!! At least they cannot claim "I didn't see it".. They are told of a close filename.. and get to abort it if its true!! ======= end of 2.39 ==== REV 2.35/36/37/38 .. Still more folishness trying to make a compatable TAG with all your various modems! HAd to change the rev... if you have a Supra... you should try this one if you are having trouble with it. We are REALLY close with this one boys and girls. The extra delays and now (with 37) delays in transmission of all modem related strings.. seems to make the modem more immune to failures than ever!! Also fixed are the special circumstances that seem to hang the BBS!! When someone calls, and the BBS gets the "CONNECT xxxx" message... and for some reason.. the user is released... the bbs would hang there for 2 minutes... now a "RING" or "NO CARRIER" message is now looked for.. and if it sees it.. the BBS will hangup the phone!! The only Visual effect is that the user must hit the RETURN a couple of times... but this will be of value when intra-mail is implimented!! REV 2.34 ... After 2 calls to SUPRA.. I have what I hope is a FIX for the infamous "won't switch back up to 2400 baud after hangup!!" problem. Anyone with a SUPRA modem should take the time to dnload this file and set thier parameter MODEMWACKS: to a minimum 20!!! I did this change at the exact specification of the engineers at Supra while maintaining a compatable posture with other, less susceptable modems in my care. This is support like you ain't never got before!!! Is this worth shareware??? Also, a late entry in the rev... you will find 4 entries in the SPECIAL parameter on the Status Pane. These are counters for things that happened "this boot". C=#calls N=#of people that JOINED F=#false calls H=#of errors while attempting to hangup. ==== END OF 2.34 ==== REV 2.33 (includes 32).. There was a particularly nasty bug remaining in the logon (out of time). When I added the item to allow the "Appealing to sysop for HELP"..(REV 2.14)... I inadvertently interfere with a computation. This is fixed in this rev... EVERYONE should upgrade as soon as possible! as your users WILL be complaining!! The bug seems only to happen if your last BBS user hit the OVERTIME LOGOFF..!! I feel it is working correctly in this rev. Sorry, but as I improve this... the complexity and chance of error advances in a NON-LINEAR fashion!! I depend on you, the BBS user to catch and report these problems!! ==== END OF REV 2.33 ===== REV 2.31 1/89 This rev has a fix for those of you who have problems with your modem not going back up to 2400 baud after a call at a lower baUD-RATE call. This, of course, olnl applies to 2400 baud users. The exact reason that this is happening is uncertain... but the modem is definitely the problem! Anyway, the fix will attempt to hangup the phone as many times as you specify and verify that the modem has switched up to its highest baud-rate. Those people who are not having this trouble should see no benefit in this rev! ====== END OF 2.31 ====== REV 2.30 1/89 This is a dressing-only rev. The Status-pane has been expandd to include many new items of interrest to the sysop. There is room for more but I felt the inclusion asap of the main items might be of interrest. Express mail optional-but-automatic is in this rev. You get a list of express mail.. and must ONLY hit return to read it. Entering anything else will get you out of express mail reading at this time. ====== END OF 2.30 ====== REV 2.29 1/89 The quick-find-new-account algorythm would leave a hole in the user list numbers. This would not have any bad effects since each reboot would find the hole and have the next new caller placed there. The algorythm is perfected in this rev.. and sequential users are once again restored with no effect on quick-find! Also the 'trivia-in' file is updated! Included are MANY new questions thanks to our friends on IrishPubBBS (Friendswood,Tx). ====== END OF 2.29 ========= REV 2.28 12/88 This rev fixes a small bug that limited the EDITING of the 'board-name' to its original 11 characters instead of its, now allowable, 14 characters. ======= END OF 2.28 ========= REV 2.27 12/88 I had noticed, and a user mentioned it... the system startup time was being reported incorrectly with the <I>nfo option off the MAIN MENU. This was an oversight from day 1. There is a PATCH in this release to fix this if you ALREADY have TAG up and running. What you must do is.... Enter the BBS as SYSOP... Set your <N>ew point to be what you want as your BBS startup date and time. Then, again from the main menu, enter 'Z'... You will get an ack message and your system startup-time will be set to the date/time in the previously set <N>ew point. This patch will just disappear in future revs as the cause of the problem has been fixed and it is intended just to patch/fix existing TAG BBSs. ------------------------- The NEW user <J>oin interplay is rewritten. No matter what I tried.. some dummy attempted to re-invent the sign-in... It is not yet dummy-proof .... but it does give edit-able user responces... I feel it will allow your users much cleaner log-on and join data entry. ======== END OF REV 2.27 ======== REV 2.25 12/88 As requested.. A parameter is provided in the Tag_System file to allow you to schedule the BBS to shut-dowm at a specific time of day. The user will be throttled in his access if he/she is on during the 'near-shutdown' period. No UPLOAD is allowed! Download is SEVERELY limited due to the approximation method of download-timing! With the exception of aproximatly 30 minutes.. you can have the board drop at any time of day. To have control.. TAG should have been started from an EXECUTE file with the following form.... ------- cd <directory that TAG is in> stack 20000 tag <what to do when tag quits> execute <this file> ------- TAG, once it sences its time to quit, will not run again for aprox 15 minutes. If you use the above script and the 'side-job' you invoke takes less than 15 mins... this execute file may be run several times. If this is a problem.. you should take other measures to insure that the 15 minutes is padded into the script! ======= END OF REV 2.25 ======= REV 2.24 The Max number of 'chat-requests-per-call' is now parameterizable! The user can bang on the <C>hat key all he wants.. if you set this parameter to 1 or 2... he will get back what he gives... and you won't be beeped out of the computer-room!! The menu bar will tell you when a 'chat-request' is active and pending but all you will see is a flash! ---------------- Also... hopefully the FIX for fixes on the LEECH-LOG stuff. I implimented floating-point in the parameters and it should be easier to use once you get it set-up. If you declare 10 to 1 ratio ... all you must do once you set the steps (read the TAG_LIBRARIES info stuff).. to change to, say, change it to 8 to 1... is change the single parameter. ==== END of 2.24 ==== REV 2.23 11/88 One thing is adressed .. the Amiga software day clock. When you run TAG for extended periods.. your software dayclock slows by 5-10 minutes / day. To correct this on a machine that has a HARDWARE clock (like an A-501 equipped machine) a parameter is provided to cause a call (via CLI) to any routine you have to adjust the clock. On an Amiga 500.. "setclock opt load" works just fine!! You will find a parameter in the TAG_SYSTEM file that allows you to provide for this!! ==== END OF REV 2.23 ===== REV 2.22 11/88 This rev comprises the step-over to Lattice 5.0. You, the user should not be overly concerned with this... but I CERTAINLY am!! Lattice has, by the release of 5.0, caused some major ripples in the programming community with its release and has, for the most part, been very helpful in making the transition bumpy but fruitful!! The compile is now fairly SMOOTH and the size of the download is SIGNIFIGANTLY smaller.. and memory requirements much smaller.. with OVERLAYS now working!! ====== END OF REV 2.22 ===== REV 2.20 11/88 This rev is a catch-up rev... sort of an emergency band-aid with a number of advantages!! First it is compiled with a Lattice technique.. OVERLAYS. Thanks to a returned call from Lattice.. this method is ready for inclusion just when I (and you) needed it the most! As you may have noticed.. the executable was on the order of 150K. This number was only to get larger and with the massive structures in TAG.. a 1 meg Amiga was getting in danger!! Well, now... when you start a configured TAG... the memory usage will be 40-50K LESS than 2.16... and with all the things to be put in.. new protocols and more, the memory usage will NOT get any more!!! Only the module you are actually EXECUTING will be OVERLAID in memory..a considderable savings!! ==== END of rev 2.20 ==== REV 2.15 11/88 A nice user's statistics menu item is added to the <S>tatistics option for sysop's eyes only. This item will allow you to view all your users in a number of 'sorted-on' ways. You must have the C: directory available with 'sort' and 'copy' available (or in the same directory as TAG). I could have written these in... but TAG is large enough as it is! You can view by User#, Board-name, U-D ratio, time-last on, and a number of others! You can sort multipilly on different fields for a nicely formatted report. You can, of cource, turn on the printer and get a hard copy! ---------------------- The previously supplied library limits to '.arc' '.zoo' '.wrp' and '.pak' has met with resistance from several users of TAG. OK-you'ze guys... now its parameterizable!! There is a parameter near the bottom of TAG_Libraries called 'POSTCONTROLS:'. With this paramater you can configure as much protection as you wish (or, by putting in '0', delete the protection)! Then you enter all the file 'postambles' you want to honor on your board. The TAG_Libraries(provided in the download) has additional helpful information and examples. REV 2.14 11/88 A new parameter has been added to the TAG_SYSTEM file called 'BUSYOUT:' and it is to hold the parameter string that will 'off-hook' your modem. The probable choice will be 'ATH1' but anything can be substituted. The string will be sent to your modem... 1. When you press 'B' while the BBS is in its 'awaiting logon' mode. This was provided for you if you want to take the phone off hook before shutting down the BBS for any reason. My modem will hold the off-hook condition even through system power-up or reset!! 2. Any time you log onto the BBS locally ('A' , '$' or 'SPACE'). This prevents a caller from ringing the phone while you are doing your sysop-stuff (like validating files/users and answering mail). This, unlike some other improvements, is my own idea and one of my BEST!! When I am trying to formulate a returned letter to a user and on the board locally... someone always seems to call and I frantically try to get out and allow the phone to answer. When you sign-off local logon or restart TAG... the phone will be placed back on-hook for you. NOTE: If you don't want this feature... do NOT put a string after the parameter!! ------------------ A 5-minute warning has been added along with the present 1-minute warning that the user is near to being disconnection because he's exausted his time limit. ------------------- A special SYSOP option is also provided... when a user out-of-time... a message "Appealing to SYSOP for HELP.." message is broadcast. The CONSOLE (sysop computer's keyboard) is scanned for 5 seconds.. if you (the sysop) want to chat or whatever.. press the 'HELP' or 'F2' key... and the user will get an additional 10 minutes.... just the same as hitting the F2 key during normal operations!! The user will get a notification and then allowed to continue! ---------------------- Search for NEW accounts has been sped up signifigantly. The BBS software KNOWS which is the highest account number. So now the search is in REVERSE order from the HIGHEST ACCOUNT. You will find that most of your NEW users will be located in THESE accounts!! Just trying to make your job easier. ---------------------- A letter writing 'warning' message has been provided to tell you that you are about out of room. There is an arbitrary limit placed on the size of a letter.. and the warning tells you its time to stop rambling!! 70+ lines should be more than enough to get your point across. ------------------------ Two new parameters have been provided in the TAG_Libraries file and an associated new command added to the library <L>ist-area commands. The parameters are to be found in the bottom of TAG_libraries.. they are 'ARCYES:' and 'ZOOYES:'.. a '1' enables and '0' disables!! If you enable one or both of these ...... 1. You must have arc (ARCYES:1) and/or zoo (ZOOYES:1) available on either your 'c' directory or the same directory as TAG. 2. You and your users will see a 'V>iew' command at the appropriate prompt. This causes the following events..... a. The file in question is copied to RAM: as 'requested.file' b. The appropriate arc or zoo is called with the 'v' option and the output re-directed to 'ram:zzzzzwork.file' c. The data is printed out to the terminal's screens. d. Both files are deleted from ram: ======= END OF 2.14 ========== REV 2.11/12/13 11/88 A number of interfaces are cleaned up in this rev. The 'find-open-account' is greatly sped up! This used to warn you of a small wait and then (if you had a LOT of users) make you wait a LONG time while it searched for an open Account Slot. Now... this job is approxamated during boot-up of TAG and the most searching that should occur is through about 10 slots... usually finding an open in 1-5 account reads!! --------------------- The Download function now will not allow anyone to START a download unless the estimated download time is less than the time the user has left in his time-limit! ===== END OF 2.11/12/13 ========== REV 2.10 10/88 The Tag_System file is expanded to include configurable HOT-KEYS for when you are in CHAT mode. The earlier TAGs had these glib phrases locked from your manipulation except with a good sector editor. So now... you enter a number of keys encoded in a parameter called CHATCOM: and after this.. enter the key # (a=1... z=26) in following data lines and the associated data to be put out when these keys (along with CONTROL key) are pressed! REV 2.09 A minor oversight was fixed. Reply to mail now supports the EXPRESS MAIL option and SYSOP forced EXPRESS MAIL (if ExpressMAil is allowed via the Tag-System parameter) ****************** * TAG 2.08 * 10/88 ****************** 1. TAG has been put on its own SCREEN. But it is a 1-bit screen! <A> It uses only HALF as much memory as before. <B> If you have the memory... it helps the BBS to multi-task with other things you, as SYSOP, may want to do with your machine while the board is running! <C> Allows you to push the screen and its windows to the bottom or, using the BACK gadget, pop the BBS system completely BEHIND the workbench screen. You can actually FORGET its running there!! 2. A 'Logoff.text' file is provided for and must be edited into the system enviornment. This will be broadcast at the time of a normal logoff of your user. 3. Private mail has a number of changes. <A> You can now pause the display when listing a letter you are editing. The only key valid (at this rev) is the space bar. The letter will pause on its own at 20 lines... and hitting any key will allow it to go on. <B> In the editor.. an extra prompt has been provided and a 'CHANGE STRING' option is added. If you choose <C>hange.. the line to edit will be listed.. and you are prompted for 'string to change' and if its found in the line... prompted for 'string to change it TO'! MORE POWER TO THE PEOPLE!! <C> EXPRESS MAIL is now implimented in all facets of mail. <1> All mail to SYSOP is automatically given EXPRESS mail status. <2> Express mail is handled exactly the same as normal E-mail except... when a user (who HAS express mail E-mail) signs on... he is presented with the E-mail immediatly. If he chooses not to delete it... it becomes just simple E-mail upon subsequent calls to your board. 4. A new item was added to the Main Menu. The <N>ew point setting!! This will affect all menus NEW option. You are presented with your present setting... which is normally the LAST time you were on the BBS and logged off... and you may advance/retard this point by any number of HOURS. 5. Many new stats items have been added/modified for the convenience and support of the sysop. Most of these are apparent to the SYSOP and won't be individually listed. <A> The one major change is in the SYSOP menu under Library support. Under the library menu.. there is now only <M>ain- tenance. This, if invoked, brings up another menu. <E>dit.. this allows editing of library entries which are selected in a number of ways with its own sub-menu. Simple experimentation will make these aparrent to you. <A>uto-Edit.. This is described earlier in the documentation and is what you should run if you copy many new files into the library for your users. It makes SIMPLE the work of adding many files to the user library. <V>alidate.. is what you will probably run MOST often. This function searches the headers and displays files your users have uploaded. It displays them and their information for you to validate for the rest of your users (give it an ACCESS value [2 or3]). 6. The title bars of BOTH the screen and the windows are used for information display. If a user is on and requests a CHAT and you were out-of-the room and missed the call bell... for the remaining time of his call.. The title bars of all the windows will show the *** CHAT REQUESTED *** status. Once you answer the chat or he hangs up... the display will go away. During normal communication.. the windows' bars will show the caller's stats. Make use of this however you see fit. It helps me know if he's calling long distance of if they are an assett or an ass while I am monitoring the board operation. The display will toggle every few seconds setting new information!! =========== END of REV 2.08 =========== ********************* * TAG BBS rev 2.04 * ********************* The LIBRARY has been changed and new features added. This upgrade will NOT affect the present files or thier descriptions (if you already have a BBS operating). The change is evident and is described in the Tag_Libraries as well as being presented here. After you set up the Tag_Libraries file as presented... you can delete the comments in these files!! ------------------------ A protection mode is provided at the sub-lib level to keep certain eyes out of certain files. If this mode is used... a sub-lib's contents (in all libraries of your bbs) will not appear to a user with less than a '3' access level. You may note that a new security level is now available for GENERAL use in security. But when specifying "sub-lib" security.. it has very special applications. The new parameter is 'SUBPROT:' and the mechanism works like this... You enter the sub-lib's number that appears in the sub-lib list after the SUBPROT: and that sub-lib will be protected from access by any user with a security level LESS THAN 3!! But... MORE than that... they will not even be able to see what data is in them. List and Catalog will not list thier contents unless the user is a level 3!! So understand... you could turn off the SUBPROT: and set the security on an entire library to '3'! The user wont be able to upload/download in this area either... but he CAN read the descriptions!! See the difference??? If you wish to not use this security avenue, simply set this parameter to a number higher than the highest sub-lib in existance on your board ('SUBPROT:9999' is a good choice)! --------------------- Please note: the NUMBER of the file you put in this parameter matches the position in the list of sub-libs in the Tag_Libraries file and it is not the actual sub-dir number that appears when the board is up and running. This is because the FIRST sub-lib is 'ALL' and must be 'ALL' for the library program to work!...and causes this parameter named to be offset by one! TAG BBS rev 2.03 9/88 Generate changed to accomodate very small BBSs. NLIBS: parameter set to '0' if you don't want to have a library is supported. TAG BBS rev 2.02 8/88 A number of small fixes repaired. Thoughts for the future... AND I mean the NEAR future..... MAYBE tomorrow..... WX-modem... Y-modem.... Z-modem... Off disk libraries (request files).... Voting booth.... Change password.... Comprehensive (possibly graphic) statistic package..... Problems... Questions... Sugestions... Call my board Chucks C.A.B. of Delaware 302-764-3186 302-764-6079 (voice)